"Thorsten Froehlich" <tho### [at] trfde> wrote:
> In article <web.40fdaab3299dc4434e6ed3100@news.povray.org> , "Tim F"
> <fen### [at] stanfordedu> wrote:
>
> > I receive the following error when issuing 'make' on a RH9 machine (the
> > build works fine on a FC2 machine, however):
>
> This certainly belongs to povray.unix ...
>

<sigh> I thought that, but as explicity described in the bug-reporting FAQ:
http://news.povray.org/povray.announce.frequently-asked-questions/thread/%3Cfpupiu02i1198jbb38i3o06hv6is1a3uar%404ax.co
m%3E/

<quote>
We insist that you first post a description of the problem in
povray.general, so that others may investigate it on their own
systems. This will aid in discovering whether it is
platform-dependent, and hopefully will also uncover some work-arounds
and a possible bugfix in the subsequent discussion from those who are
familiar with the POV-Ray source code.
</quote>

>
> Either way, from the messages (the warnings in particular) it seems for some
> odd reason the from config.h (the cone from zlib rather than POV-Ray's) gets
> included all over the place.  I don't know why this would happen on one
> system but not another.
>

From looking around a bit, the zlib libraries did *NOT* need be built on my
FC2 machine, but were required in the RH9 machine - therefore, the
.../libraries/zlib path was included during the build, which was causing the
problem.

This raises another question - why not leave the image library dependencies
external, and just not include them with the release?

> If you want to work around it quickly I would suggest you rename the
> config.h in its directory and then build everything again.  Correct the name
> of the config.h in the zlib files that will certainly report an eror and you
> should be all set.
>

I renamed config.h in the /unix directory, changed all the #includes, and
the build worked. However, I wouldn't consider it a proper solution.

Regards,
Tim

Post a reply to this message